Node / meshtastic / Meshtastic-Android / files / .github / agents / speckit.taskstoissues.agent.md

Displaying Rendered • View raw • Download

description: Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

tools: ['github/github-mcp-server/issue_write']

T282828

You MUST consider the user input before proceeding (if not empty).

Check for extension hooks (before tasks-to-issues conversion):

• Check if T383838.specify/extensions.yml exists in the project root.

• If it exists, read it and look for entries under the T383838hooks.before_taskstoissues key

• If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally

• Filter out hooks where T383838enabled is explicitly T383838false. Treat hooks without an T383838enabled field as enabled by default.

• For each remaining hook, do not attempt to interpret or evaluate hook T383838condition expressions:

• If the hook has no T383838condition field, or it is null/empty, treat the hook as executable

• If the hook defines a non-empty T383838condition, skip the hook and leave condition evaluation to the HookExecutor implementation

• For each executable hook, output the following based on its T383838optional flag:

• Optional hook (T383838optional: true):

T282828

• Mandatory hook (T383838optional: false):

T282828

• If no hooks are registered or T383838.specify/extensions.yml does not exist, skip silently

1. Run T383838.specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks from repo root and parse FEATUREDIR and AVAILABLEDOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\''m Groot' (or double-quote if possible: "I'm Groot").

1. From the executed script, extract the path to tasks.

1. Get the Git remote by running:

T282828

│ [!CAUTION] ONLY PROCEED TO NEXT STEPS IF THE REMOTE IS A GITHUB URL

1. For each task in the list, use the GitHub MCP server to create a new issue in the repository that is representative of the Git remote.

│ [!CAUTION] UNDER NO CIRCUMSTANCES EVER CREATE ISSUES IN REPOSITORIES THAT DO NOT MATCH THE REMOTE

│ URL

Check for extension hooks (after tasks-to-issues conversion):

Check if T383838.specify/extensions.yml exists in the project root.

• If it exists, read it and look for entries under the T383838hooks.after_taskstoissues key

• If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally

• Filter out hooks where T383838enabled is explicitly T383838false. Treat hooks without an T383838enabled field as enabled by default.

• For each remaining hook, do not attempt to interpret or evaluate hook T383838condition expressions:

• If the hook has no T383838condition field, or it is null/empty, treat the hook as executable

• If the hook defines a non-empty T383838condition, skip the hook and leave condition evaluation to the HookExecutor implementation

• For each executable hook, output the following based on its T383838optional flag:

• Optional hook (T383838optional: true):

T282828

• Mandatory hook (T383838optional: false):

T282828

• If no hooks are registered or T383838.specify/extensions.yml does not exist, skip silently